Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: don't emit an error log if pipeline is closed #1658

Conversation

wyfo
Copy link
Contributor

@wyfo wyfo commented Dec 11, 2024

Before, there was no distinction between the pipeline dropping a message because its deadline was reached or because the transport was closed.
As a consequence, blocking message which was dropped because of closed transport would still emit an error log. This PR introduce the distinction between the two dropping causes.

Before, there was no distinction between the pipeline dropping a
message because its deadline was reached or because the transport was
closed.
As a consequence, blocking message which was dropped because of
closed transport would still emit an error log. This PR introduce
the distinction between the two dropping causes.
Copy link

PR missing one of the required labels: {'enhancement', 'internal', 'bug', 'breaking-change', 'dependencies', 'new feature', 'documentation'}

@wyfo wyfo added bug Something isn't working internal Changes not included in the changelog labels Dec 11, 2024
@wyfo wyfo requested review from Mallets and yellowhatter December 11, 2024 10:52
@Mallets Mallets merged commit df86f75 into eclipse-zenoh:main Dec 11, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working internal Changes not included in the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants